Skip to content

Third attempt at fixing Kotlin 2.2 compat #4613

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

adinauer
Copy link
Member

@adinauer adinauer commented Aug 7, 2025

📜 Description

💡 Motivation and Context

💚 How did you test it?

📝 Checklist

  • I added tests to verify the changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • Review from the native team if needed.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

Copy link
Contributor

github-actions bot commented Aug 7, 2025

Fails
🚫 Please consider adding a changelog entry for the next release.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

- Third attempt at fixing Kotlin 2.2 compat ([#4613](https://github.com/getsentry/sentry-java/pull/4613))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description.

Generated by 🚫 dangerJS against 8d5bfcf

@adinauer adinauer marked this pull request as ready for review August 7, 2025 14:34
@adinauer adinauer merged commit 1d5a803 into 08-06-second_attempt_to_fix_kotlin_2.2 Aug 7, 2025
18 of 37 checks passed
@adinauer adinauer deleted the 08-07-third_attempt_at_fixing_kotlin_2.2_compat branch August 7, 2025 14:34
@adinauer
Copy link
Member Author

adinauer commented Aug 7, 2025

Merging this so we don't have to review changes in other PRs that were replaced in this PR

adinauer added a commit that referenced this pull request Aug 7, 2025
* Second attempt to fix Kotlin 2.2

* Format code

* Third attempt at fixing Kotlin 2.2 compat (#4613)

---------

Co-authored-by: Sentry Github Bot <[email protected]>
@@ -145,7 +145,7 @@ fun toRequestUrl(uri: URI): StringBuffer? {
url.append(':').append(port)
}

if (uri?.isNotBlank()) {
if (uri.isNotBlank()) {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Null URI Handling Error

A NullPointerException can occur because the null-safe call uri?.isNotBlank() was changed to uri.isNotBlank(). The uri variable is assigned from URI.rawPath, which can return null when the URI has no path component, removing the necessary null check.

Fix in Cursor Fix in Web

adinauer added a commit that referenced this pull request Aug 11, 2025
* Fix Spring 7 and Spring Boot 4 modules

* Attempt to fix kotlin 2.2 issue

* Second attempt to fix Kotlin 2.2 (#4610)

* Second attempt to fix Kotlin 2.2

* Format code

* Third attempt at fixing Kotlin 2.2 compat (#4613)

---------

Co-authored-by: Sentry Github Bot <[email protected]>

* Address compose-related issues

* Fix tests for Spring 7 and Spring Boot 4 (#4614)

* Second attempt to fix Kotlin 2.2

* Format code

* Third attempt at fixing Kotlin 2.2 compat

* Fix tests for Spring 7 and Spring Boot 4

* Move Spring 7 and Spring Boot 4 packages (#4615)

* Move Spring 7 and Spring Boot 4 packages

* Fix class not found due to OTel not supporting spring boot 4 yet (#4616)

* Format code

* some fixes

* change kotlin 1.8 to 1.9 and some cleanup

* ignore warnings about api level that is not relevant

* fix optional dependencies in SentryAutoConfiguration

* Update trace origin

* Remove duplicate e2e test config

* Update Strings for Spring 7 and Spring Boot 4

* Disable Spring Boot 4 agentless e2e tests for now

---------

Co-authored-by: Sentry Github Bot <[email protected]>

---------

Co-authored-by: Sentry Github Bot <[email protected]>
Co-authored-by: markushi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant